Investigating design anti-pattern and design pattern mutations and their change- and fault-proneness

During software evolution, inexperienced developers may introduce design anti-patterns when they modify their systems to fix bugs or add new functionalities based on changes in requirements. Developers also use patterns promote quality as a possible cure for some anti-patterns. Thus, and are introduced, removed, mutated from one another by developers. Many studies investigated the evolution of impact development. However, isolation did not consider mutations these quality. Therefore, we report our study bidirectional between impacts change- fault-proneness. We analyzed snapshots seven Java with diverse sizes, histories, application domains. built Markov models capture probability occurrences different mutations. Results show that (1) mutate into other and–or They (2) change types primarily trigger (renaming comments, declarations, operators), (3) more faulty specific contexts. These results provide important insights its fault-proneness systems.